Hello, Is there any way to reduce size of C:\Windows\winsxs folder in windows 2008 R2 simular to DISM /online /Cleanup-Image /SpSuperseded ? Many thanks

Hello, Vasily K. You read this? Regards.Oscar Abad -- MCITP Enterprise Administrator // MCITP Server Administrator

Yes, I did but It does not work for windows 2008 R2 even if you install and use cleanmgr. this article was the most usefull: __http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-reclaim-space-after-applying-service-pack-1.aspx but it does not work for windows 2008 R2 without sp1.

Review this. Maybe....Oscar Abad -- MCITP Enterprise Administrator // MCITP Server Administrator

Hi, The only way to safely reduce the size of the WinSxS folder is to reduce the set of possible actions that the system can take – the easiest way to do that is to remove the packages that installed the components in the first place. This can be done by uninstalling superseded versions of packages that are on your system. Service Pack 1 contains a binary called VSP1CLN.EXE, a tool that will make the Service Pack package permanent (not removable) on your system, and remove the RTM versions of all superseded components. This can only be done because by making the Service Pack permanent we can guarantee that we won’t ever need the RTM versions. For the detailed information, please refer to the following Microsoft TechNet blog: What is the WINSXS directory in Windows 2008 and Windows Vista and why is it so large? http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, The only way to safely reduce the size of the WinSxS folder is to reduce the set of possible actions that the system can take – the easiest way to do that is to remove the packages that installed the components in the first place. This can be done by uninstalling superseded versions of packages that are on your system. Service Pack 1 contains a binary called VSP1CLN.EXE, a tool that will make the Service Pack package permanent (not removable) on your system, and remove the RTM versions of all superseded components. This can only be done because by making the Service Pack permanent we can guarantee that we won’t ever need the RTM versions. For the detailed information, please refer to the following Microsoft TechNet blog: What is the WINSXS directory in Windows 2008 and Windows Vista and why is it so large? http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx Regards, Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Article above was written in 2008, now it is 2011. Are you saying what there is still no legitimate way to fix it for windows server 2008/ 2008 R2?

Hi, The WinSxS folder in both Windows Server 2008 and Windows Server 2008 R2 are working within the same mechanism. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Question was not answered properly. If there is no solution at least Microsoft could recommend to use minimum partitions for OS drive 50 GB for windows server 2008, otherwise it is misleading.

This is ridiculous. Users should have the option of removing old components. The claim that the vast majority of the WINSXS directory doesn't actually take space is a lie. Our WINSXS directory is over 8.5 GB. The amount of space used by hardlinks is 2.6 GB. On our basic IIS server, over 69% of the space taken by WINSXS is actually taken. Installing SP1 and then running the cleanup tool may help a bit, but it's not a permanent solution. A permanent solution would be to allow users to delete all that crap. The vast majority of users will never have a broken/missing component from an out-of-order install/uninstall process. Those that do can simply (get this!) reinstall the component, either manually or by reinstalling the service/feature/role/software/update that gave it to them. The current system is just absurd. Yes, it's nice to have a manifest of what version of what works with what. No, it's not necessary to actually store the damned unused files on the system drive when everyone is using a small partition, in accordance with MS's recommendations! Let people get the files on their own if they need them. Windows update? OS DVD? Optional storage of OS DVD contents (similar to the i386 folder for XP)? Reinstalling the thing that gave them that component version? Of course, it's too late now. What can be done now is an option to clear out unused components and prevent them from being stored in the future. Put a big ol' warning on it that says "If you, or an update to a program/feature/service/etc., breaks something, you'll have to roll back!".